bitkeeper revision 1.7.3.34 (3e01bea4NFTKk3m4icWUc3KR11_-HQ)

removing printks

diff --git a/xenolinux-2.4.16-sparse/arch/xeno/drivers/dom0/dom0_memory.c b/xenolinux-2.4.16-sparse/arch/xeno/drivers/dom0/dom0_memory.c
index 87cbfb0483a1f68bfa5e3b35a6034e71fbfdc1fa..87fdb42142a12ee44f3328e78b49054edcf7bd26 100644 (file)
--- a/xenolinux-2.4.16-sparse/arch/xeno/drivers/dom0/dom0_memory.c
+++ b/xenolinux-2.4.16-sparse/arch/xeno/drivers/dom0/dom0_memory.c
@@ -20,6 +20,12 @@
 #define MAP_CONT    0
 #define MAP_DISCONT 1
 
+/* now, this is grimm, kmalloc seems to have problems allocating small mem
+ * blocks, so i have decided to use fixed (a bit) larger blocks... this needs
+ * to be traced down but no time now.
+ */
+#define KMALLOC_SIZE   128
+
 /*
  * maps a range of physical memory into the requested pages. the old
  * mappings are removed. any references to nonexistent pages results
@@ -178,13 +184,9 @@ unsigned long direct_mmap(unsigned long phys_addr, unsigned long size,
         goto out;
     }
 
-       printk(KERN_ALERT "bd240 debug: before kmalloc\n");
-
     /* add node on the list of directly mapped areas */ 
     //dmmap = (direct_mmap_node_t *)kmalloc(GFP_KERNEL, sizeof(direct_mmap_node_t));
-    dmmap = (direct_mmap_node_t *)kmalloc(GFP_KERNEL, 128);
-
-       printk(KERN_ALERT "bd240 debug: after kmalloc\n");
+    dmmap = (direct_mmap_node_t *)kmalloc(GFP_KERNEL, KMALLOC_SIZE);
 
     dmmap->addr = addr;
     list_add(&dmmap->list, &current->mm->context.direct_list);